Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa82636ed17ad944b92175056945d205381f208f2414dd0dd4ca32621703915

Tx prefix hash: bb500326d7fa32a0f6d3577cc770465be2c51e6fa2dfce92f2631e58e626f7b4
Tx public key: 27c591b8401a3fe06da81059d9714c51402f1d8b6d15b33b037bd804c3e3985e
Timestamp: 1764845020 Timestamp [UCT]: 2025-12-04 10:43:40 Age [y:d:h:m:s]: 00:034:20:16:44
Block: 1426215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24954 RingCT/type: yes/0
Extra: 0127c591b8401a3fe06da81059d9714c51402f1d8b6d15b33b037bd804c3e3985e021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f211492d1ad7e9d34255fdef42f44a24280d105efc2af8e94c4007a011e4f297 0.600000000000 1914904 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": 1426225, "vin": [ { "gen": { "height": 1426215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f211492d1ad7e9d34255fdef42f44a24280d105efc2af8e94c4007a011e4f297" } } ], "extra": [ 1, 39, 197, 145, 184, 64, 26, 63, 224, 109, 168, 16, 89, 217, 113, 76, 81, 64, 47, 29, 139, 109, 21, 179, 59, 3, 123, 216, 4, 195, 227, 152, 94, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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