Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a0afe765352a2866a83a6f21347b45577f843d4052181a2bca7c90c3f2cf667

Tx prefix hash: bc86e30a1780c87eaee6d9c473948b2f11f0ec6c6d2aaf168df4d7d2dbc9d9e3
Tx public key: 778af893af2fbca871019bc4f1b1dddff6e78c353b06ab8acf6e5e1692a7572e
Timestamp: 1700433914 Timestamp [UCT]: 2023-11-19 22:45:14 Age [y:d:h:m:s]: 01:100:15:02:51
Block: 895347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333056 RingCT/type: yes/0
Extra: 01778af893af2fbca871019bc4f1b1dddff6e78c353b06ab8acf6e5e1692a7572e02110000000fe6d27f9c000000000000000000

1 output(s) for total of 0.662740793000 dcy

stealth address amount amount idx
00: bb6f8060ecb2581d4fc43a38aa4ca83f172409d16dd02402d6be956f83965e19 0.662740793000 1351578 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": 895357, "vin": [ { "gen": { "height": 895347 } } ], "vout": [ { "amount": 662740793, "target": { "key": "bb6f8060ecb2581d4fc43a38aa4ca83f172409d16dd02402d6be956f83965e19" } } ], "extra": [ 1, 119, 138, 248, 147, 175, 47, 188, 168, 113, 1, 155, 196, 241, 177, 221, 223, 246, 231, 140, 53, 59, 6, 171, 138, 207, 110, 94, 22, 146, 167, 87, 46, 2, 17, 0, 0, 0, 15, 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