Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 669866ea5b30aee270d4f5377b46945d6900dc7a507a6d5ed348b0e109dca3d4

Tx prefix hash: e8456dbe09c734f98646781d3dad7f11418c7eb78b6059c6f492115d52e7f2cb
Tx public key: abeb82924d2ab5611a8e41e505da7e91cc90a2720da132dfd27a1e06f737f174
Timestamp: 1719344842 Timestamp [UCT]: 2024-06-25 19:47:22 Age [y:d:h:m:s]: 00:287:21:14:04
Block: 1052112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205720 RingCT/type: yes/0
Extra: 01abeb82924d2ab5611a8e41e505da7e91cc90a2720da132dfd27a1e06f737f1740211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52d73962b9dea7b8e06a1f021c52f7e8dbd5d667489764bf3a5ef99ca02a22b7 0.600000000000 1522433 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": 1052122, "vin": [ { "gen": { "height": 1052112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52d73962b9dea7b8e06a1f021c52f7e8dbd5d667489764bf3a5ef99ca02a22b7" } } ], "extra": [ 1, 171, 235, 130, 146, 77, 42, 181, 97, 26, 142, 65, 229, 5, 218, 126, 145, 204, 144, 162, 114, 13, 161, 50, 223, 210, 122, 30, 6, 247, 55, 241, 116, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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