Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 567b96951670643d0748f5a133f9b4ad015466d3656579a7b8182cfdc412ef50

Tx prefix hash: eaef9443096aaba3983960120d87ea5cd34c1abaceffa45a7b73a0d8162b763d
Tx public key: b62fe88bd2840bdb6aa1138fae4eab0c6fd7a6f91090d3976a1a09b2fbf4aef9
Timestamp: 1703217561 Timestamp [UCT]: 2023-12-22 03:59:21 Age [y:d:h:m:s]: 01:323:20:45:02
Block: 918417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490313 RingCT/type: yes/0
Extra: 01b62fe88bd2840bdb6aa1138fae4eab0c6fd7a6f91090d3976a1a09b2fbf4aef902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ad34a28870a136ae7258605cf954fc7c6d2890bdba777fe985970dc0a976bb1 0.600000000000 1376061 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": 918427, "vin": [ { "gen": { "height": 918417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ad34a28870a136ae7258605cf954fc7c6d2890bdba777fe985970dc0a976bb1" } } ], "extra": [ 1, 182, 47, 232, 139, 210, 132, 11, 219, 106, 161, 19, 143, 174, 78, 171, 12, 111, 215, 166, 249, 16, 144, 211, 151, 106, 26, 9, 178, 251, 244, 174, 249, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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