Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e65ad3470df0606ecec2f5fb98e356fdf68cc8fdbd9c0ed893299e23fdefb16

Tx prefix hash: 7ca98b2cb30d2290a8220d534d1669aa7e30051b4e18deb3bda9cc1764437d8c
Tx public key: e810d8ed51cf52132edcfcb41d45a12ffaa6dc96202a5b1ea4ee03af64320c61
Timestamp: 1699213224 Timestamp [UCT]: 2023-11-05 19:40:24 Age [y:d:h:m:s]: 01:083:01:27:17
Block: 885223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320685 RingCT/type: yes/0
Extra: 01e810d8ed51cf52132edcfcb41d45a12ffaa6dc96202a5b1ea4ee03af64320c61021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.715959956000 dcy

stealth address amount amount idx
00: deb4666216f11ee707eed4fb7456cad15eaec515414d80b5512040298f12f1c4 0.715959956000 1340984 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": 885233, "vin": [ { "gen": { "height": 885223 } } ], "vout": [ { "amount": 715959956, "target": { "key": "deb4666216f11ee707eed4fb7456cad15eaec515414d80b5512040298f12f1c4" } } ], "extra": [ 1, 232, 16, 216, 237, 81, 207, 82, 19, 46, 220, 252, 180, 29, 69, 161, 47, 250, 166, 220, 150, 32, 42, 91, 30, 164, 238, 3, 175, 100, 50, 12, 97, 2, 17, 0, 0, 0, 2, 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