Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f30e87b4fe7b3cb7fe807003a8663af8da672b32ca4cf698350ab01ea76f49d

Tx prefix hash: dbf02d1890939ff09254fe0d3da90906bf6221d62acef5d70ce5fe83a831784b
Tx public key: 1def21a7937d73d9363b9553a347bd8ea030b102f6928cd9349e418a4d21fe22
Timestamp: 1576619135 Timestamp [UCT]: 2019-12-17 21:45:35 Age [y:d:h:m:s]: 04:338:09:51:48
Block: 27984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128984 RingCT/type: yes/0
Extra: 011def21a7937d73d9363b9553a347bd8ea030b102f6928cd9349e418a4d21fe2202110000001f4ac5aa02000000000000000000

1 output(s) for total of 495.785252081000 dcy

stealth address amount amount idx
00: ea4040c0110fd1b4946f77c487a8f0c2492c1608ef96bee62180f3fc64c34cec 495.785252081000 46410 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": 27994, "vin": [ { "gen": { "height": 27984 } } ], "vout": [ { "amount": 495785252081, "target": { "key": "ea4040c0110fd1b4946f77c487a8f0c2492c1608ef96bee62180f3fc64c34cec" } } ], "extra": [ 1, 29, 239, 33, 167, 147, 125, 115, 217, 54, 59, 149, 83, 163, 71, 189, 142, 160, 48, 177, 2, 246, 146, 140, 217, 52, 158, 65, 138, 77, 33, 254, 34, 2, 17, 0, 0, 0, 31, 74, 197, 170, 2, 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