Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09f875d0fa2901a6b652bf977e807f95cd827d5d01ddf2c2a80b620bca45831d

Tx prefix hash: 3cb83439747e02e53a7a75c1990336a67cb70a675a73ae317fc9ab4a061c01a4
Tx public key: f6677ccfc8856c10026b0fcabe5e501b881a0170ed8974783e89179feb6f1055
Timestamp: 1721924616 Timestamp [UCT]: 2024-07-25 16:23:36 Age [y:d:h:m:s]: 00:243:19:38:31
Block: 1073506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174157 RingCT/type: yes/0
Extra: 01f6677ccfc8856c10026b0fcabe5e501b881a0170ed8974783e89179feb6f105502110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ff5c0183cf06a01e107b796ef1b331cb3abcca0c014daf13a8e15f33d78d26f 0.600000000000 1546009 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": 1073516, "vin": [ { "gen": { "height": 1073506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ff5c0183cf06a01e107b796ef1b331cb3abcca0c014daf13a8e15f33d78d26f" } } ], "extra": [ 1, 246, 103, 124, 207, 200, 133, 108, 16, 2, 107, 15, 202, 190, 94, 80, 27, 136, 26, 1, 112, 237, 137, 116, 120, 62, 137, 23, 159, 235, 111, 16, 85, 2, 17, 0, 0, 0, 15, 233, 20, 221, 21, 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