Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ae9e6bbb0ea239eb62b3a793e27c72e0b9f41db213e605ad1a0e38f2a6b95b

Tx prefix hash: 53a7c28fd36b90a1db95abb9dc4517711642dde215c5bc8bb87390f043fc47d4
Tx public key: 683177345630888a0ef9c67ce686a89fbcf6e56111ecea9202b6f80bcdbb7f40
Timestamp: 1714310832 Timestamp [UCT]: 2024-04-28 13:27:12 Age [y:d:h:m:s]: 01:193:01:33:54
Block: 1010387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396622 RingCT/type: yes/0
Extra: 01683177345630888a0ef9c67ce686a89fbcf6e56111ecea9202b6f80bcdbb7f4002110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c45161e477cc2a9c75087e8df28e2e28204cd338f09c86a12bf8b7b81f61641 0.600000000000 1472325 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": 1010397, "vin": [ { "gen": { "height": 1010387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c45161e477cc2a9c75087e8df28e2e28204cd338f09c86a12bf8b7b81f61641" } } ], "extra": [ 1, 104, 49, 119, 52, 86, 48, 136, 138, 14, 249, 198, 124, 230, 134, 168, 159, 188, 246, 229, 97, 17, 236, 234, 146, 2, 182, 248, 11, 205, 187, 127, 64, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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