Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d3755fb320859f8c1966bbb33feea1bd5bfdf67afa23d4905edf0af7b4f4473

Tx prefix hash: bde9838c50b9276dd8169258e53f803581acdc5ca74c6b203b7b3a4053d8ee23
Tx public key: a090717963b93eaee5565b984a79f5d5c3fcb1f196977aa44e474920dbe9c086
Timestamp: 1729698504 Timestamp [UCT]: 2024-10-23 15:48:24 Age [y:d:h:m:s]: 00:140:19:34:42
Block: 1137938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100438 RingCT/type: yes/0
Extra: 01a090717963b93eaee5565b984a79f5d5c3fcb1f196977aa44e474920dbe9c086021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 021c5cb55d704047efbf6192ef35e21d788f14e606e7447d4a666df60da767b5 0.600000000000 1621525 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": 1137948, "vin": [ { "gen": { "height": 1137938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "021c5cb55d704047efbf6192ef35e21d788f14e606e7447d4a666df60da767b5" } } ], "extra": [ 1, 160, 144, 113, 121, 99, 185, 62, 174, 229, 86, 91, 152, 74, 121, 245, 213, 195, 252, 177, 241, 150, 151, 122, 164, 78, 71, 73, 32, 219, 233, 192, 134, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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