Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 67b99674aba0ecb6fb0f02a0f755a2606960931f814663b93834986cd5c7a301

Tx prefix hash: a35e6d39fc36a17de4e922d86fa62ea4e1711366522320040dd59792e536a080
Tx public key: 031278b3d4fee650fa8a0c37e5c487bf1aeeb4117ab312479bc8a96bcd7891d9
Timestamp: 1722671914 Timestamp [UCT]: 2024-08-03 07:58:34 Age [y:d:h:m:s]: 00:174:06:31:43
Block: 1079713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124628 RingCT/type: yes/0
Extra: 01031278b3d4fee650fa8a0c37e5c487bf1aeeb4117ab312479bc8a96bcd7891d902110000001591e13c04000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: 8ebe30d7e625c6a8b861eeebf12839341183c1ce52b9d9c5e69199b2d5b4edb2 0.615600000000 1552784 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1079723, "vin": [ { "gen": { "height": 1079713 } } ], "vout": [ { "amount": 615600000, "target": { "key": "8ebe30d7e625c6a8b861eeebf12839341183c1ce52b9d9c5e69199b2d5b4edb2" } } ], "extra": [ 1, 3, 18, 120, 179, 212, 254, 230, 80, 250, 138, 12, 55, 229, 196, 135, 191, 26, 238, 180, 17, 122, 179, 18, 71, 155, 200, 169, 107, 205, 120, 145, 217, 2, 17, 0, 0, 0, 21, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8