Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73e9fd4f0e52f69eb43ed33308792be8a22cf7140cb6ccc7d93371d96772637c

Tx prefix hash: fb5e3b0c7b4a1a201259c2efbffaf51c22d346a43551eedcb2998137b3fe9aa1
Tx public key: 837df2823c3ce9f8b99d0c4aa4601df05b7109b6b6cb97280e69277366d5ccf8
Timestamp: 1700043561 Timestamp [UCT]: 2023-11-15 10:19:21 Age [y:d:h:m:s]: 01:196:16:25:49
Block: 892102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401800 RingCT/type: yes/0
Extra: 01837df2823c3ce9f8b99d0c4aa4601df05b7109b6b6cb97280e69277366d5ccf8021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.679353379000 dcy

stealth address amount amount idx
00: e4f76eb88e14e1d1ebdda2ed2e0a6bfedf3ac003cb150650481f1a0142d3533d 0.679353379000 1348163 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": 892112, "vin": [ { "gen": { "height": 892102 } } ], "vout": [ { "amount": 679353379, "target": { "key": "e4f76eb88e14e1d1ebdda2ed2e0a6bfedf3ac003cb150650481f1a0142d3533d" } } ], "extra": [ 1, 131, 125, 242, 130, 60, 60, 233, 248, 185, 157, 12, 74, 164, 96, 29, 240, 91, 113, 9, 182, 182, 203, 151, 40, 14, 105, 39, 115, 102, 213, 204, 248, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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