Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49b3db3bc4b099792bd5335c395be24df4a7ae3f374e58dcd0a0cd6431cae966

Tx prefix hash: 35320aa80bc687882462b0d8ffe7c74957c07a1b3d15bd02417ee13e52a3d953
Tx public key: 2066b2d17d366fe34bc12dccea361a237ae5778bb4e5ed3d3d2caf78446ff98c
Timestamp: 1753020438 Timestamp [UCT]: 2025-07-20 14:07:18 Age [y:d:h:m:s]: 00:111:19:26:10
Block: 1329562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78712 RingCT/type: yes/0
Extra: 012066b2d17d366fe34bc12dccea361a237ae5778bb4e5ed3d3d2caf78446ff98c021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63f72e682e051ee9ecd69e38fea85f2808c722643b9249c0c8be3ddf915f7610 0.600000000000 1817339 of 15

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": 1329572, "vin": [ { "gen": { "height": 1329562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63f72e682e051ee9ecd69e38fea85f2808c722643b9249c0c8be3ddf915f7610" } } ], "extra": [ 1, 32, 102, 178, 209, 125, 54, 111, 227, 75, 193, 45, 204, 234, 54, 26, 35, 122, 229, 119, 139, 180, 229, 237, 61, 61, 44, 175, 120, 68, 111, 249, 140, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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