Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 772e8f25eb5b54847057476b48f4ab9d72bd44551aa6bf19e541dd204274c1f9

Tx prefix hash: b645793ca4508d4a85cb171b32c920d6d0b2e22f3b26aaccb55542ec3be6f8b5
Tx public key: 590e775337e3fb217370f9fbae3552b2dbe2c9fa9abe59dafdf8d094e326bfe8
Timestamp: 1697198621 Timestamp [UCT]: 2023-10-13 12:03:41 Age [y:d:h:m:s]: 01:169:14:35:34
Block: 868722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382241 RingCT/type: yes/0
Extra: 01590e775337e3fb217370f9fbae3552b2dbe2c9fa9abe59dafdf8d094e326bfe802110000000633af99f4000000000000000000

1 output(s) for total of 0.812013818000 dcy

stealth address amount amount idx
00: d3a5f67c945a2aa9011848787240b7cc18f8c9f7af9af94e54c68b26a85985b0 0.812013818000 1323541 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": 868732, "vin": [ { "gen": { "height": 868722 } } ], "vout": [ { "amount": 812013818, "target": { "key": "d3a5f67c945a2aa9011848787240b7cc18f8c9f7af9af94e54c68b26a85985b0" } } ], "extra": [ 1, 89, 14, 119, 83, 55, 227, 251, 33, 115, 112, 249, 251, 174, 53, 82, 178, 219, 226, 201, 250, 154, 190, 89, 218, 253, 248, 208, 148, 227, 38, 191, 232, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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