Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dd7e5867a69c5676ce9501cc7ac7fdb3c1cb97f8c907f23220e42cc3acd1344

Tx prefix hash: 6d2f2485c7bb0491758663ab17cabae12364b730a388547d8ccb2859fcee6743
Tx public key: 63a497430dcc9ae52d2e3b853d8f240ea5ab8788ad071e87437c48b2f537ba91
Timestamp: 1721464582 Timestamp [UCT]: 2024-07-20 08:36:22 Age [y:d:h:m:s]: 00:298:13:20:18
Block: 1069693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213337 RingCT/type: yes/0
Extra: 0163a497430dcc9ae52d2e3b853d8f240ea5ab8788ad071e87437c48b2f537ba910211000000014385362a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a503ae452fa24666efc9c76253a4dffa67c06b78d6a42d69f8d5b91bad5c85b 0.600000000000 1541226 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": 1069703, "vin": [ { "gen": { "height": 1069693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a503ae452fa24666efc9c76253a4dffa67c06b78d6a42d69f8d5b91bad5c85b" } } ], "extra": [ 1, 99, 164, 151, 67, 13, 204, 154, 229, 45, 46, 59, 133, 61, 143, 36, 14, 165, 171, 135, 136, 173, 7, 30, 135, 67, 124, 72, 178, 245, 55, 186, 145, 2, 17, 0, 0, 0, 1, 67, 133, 54, 42, 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