Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f4fe2e27b835009b7f7e9376fe5b32f6422d8c04e4c9dec2a74554916c847e8

Tx prefix hash: 0c15286800b6320d5aaf71327f49fd094a58455d1bea9fa676df2c91a799773a
Tx public key: 4b59121e5fb737560e75f63313c8f216cf1984846a51569e48e6db3be265f802
Timestamp: 1577438537 Timestamp [UCT]: 2019-12-27 09:22:17 Age [y:d:h:m:s]: 05:135:03:21:14
Block: 32780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1246384 RingCT/type: yes/0
Extra: 014b59121e5fb737560e75f63313c8f216cf1984846a51569e48e6db3be265f8020211000000014ac5aa02000000000000000000

1 output(s) for total of 477.965491553000 dcy

stealth address amount amount idx
00: b6937ff000eae1b3a14782011bee290580b908c69fb2462a7f525028867956f7 477.965491553000 54595 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": 32790, "vin": [ { "gen": { "height": 32780 } } ], "vout": [ { "amount": 477965491553, "target": { "key": "b6937ff000eae1b3a14782011bee290580b908c69fb2462a7f525028867956f7" } } ], "extra": [ 1, 75, 89, 18, 30, 95, 183, 55, 86, 14, 117, 246, 51, 19, 200, 242, 22, 207, 25, 132, 132, 106, 81, 86, 158, 72, 230, 219, 59, 226, 101, 248, 2, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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