Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bc9c512349265f918eb6b4488293f4d9e79998e37bdd8fde5c53bacea7bfde7

Tx prefix hash: b315fb3f2929183832d7c9c592b381a1f1b3ebaa9c7226e518d6d531c1a699b3
Tx public key: 106a293ec0adcf7b16a0d29fd724de4e09bd57164ed487e4f8bcdfe67f58eba7
Timestamp: 1702120372 Timestamp [UCT]: 2023-12-09 11:12:52 Age [y:d:h:m:s]: 01:122:03:37:22
Block: 909320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348449 RingCT/type: yes/0
Extra: 01106a293ec0adcf7b16a0d29fd724de4e09bd57164ed487e4f8bcdfe67f58eba702110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eb3473e80022a0a34f1b7108dfb03a0a6ec15916645eda8c198e5e29f2c8aa2 0.600000000000 1366401 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": 909330, "vin": [ { "gen": { "height": 909320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eb3473e80022a0a34f1b7108dfb03a0a6ec15916645eda8c198e5e29f2c8aa2" } } ], "extra": [ 1, 16, 106, 41, 62, 192, 173, 207, 123, 22, 160, 210, 159, 215, 36, 222, 78, 9, 189, 87, 22, 78, 212, 135, 228, 248, 188, 223, 230, 127, 88, 235, 167, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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