Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 002247fd7993f2f90f7aecaec173066ba1ed27e4a874ff2a946a3b0f0164c5a2

Tx prefix hash: 1edc5bc8540bc16c40e5e952fb0c330e52c1207cbb9443acd7c51509419998cb
Tx public key: e5c22fcde7edfc889e4efbc5df265d7e3e36f9805591397f41d5da1caeb75860
Timestamp: 1732315268 Timestamp [UCT]: 2024-11-22 22:41:08 Age [y:d:h:m:s]: 00:136:17:59:34
Block: 1159564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97542 RingCT/type: yes/0
Extra: 01e5c22fcde7edfc889e4efbc5df265d7e3e36f9805591397f41d5da1caeb75860021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c3484aeeb126fa2573c8b8af0f2ed0e3a31339beec9dc11a5fcdcee8288937d 0.600000000000 1645203 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": 1159574, "vin": [ { "gen": { "height": 1159564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c3484aeeb126fa2573c8b8af0f2ed0e3a31339beec9dc11a5fcdcee8288937d" } } ], "extra": [ 1, 229, 194, 47, 205, 231, 237, 252, 136, 158, 78, 251, 197, 223, 38, 93, 126, 62, 54, 249, 128, 85, 145, 57, 127, 65, 213, 218, 28, 174, 183, 88, 96, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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