Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2c32549d74db1b8158c5befc563ba65bf2f5e14601aa41bf31821791a64672e

Tx prefix hash: 836d7bd751176763845e0c9bd089340431836e1f67e0361b6b056bee2af85274
Tx public key: 686d49b97cb05ba6a3c7a033391e16d24baa97289a1a81bf7529d4b98a3d0b6d
Timestamp: 1734935051 Timestamp [UCT]: 2024-12-23 06:24:11 Age [y:d:h:m:s]: 00:178:23:52:23
Block: 1181286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127593 RingCT/type: yes/0
Extra: 01686d49b97cb05ba6a3c7a033391e16d24baa97289a1a81bf7529d4b98a3d0b6d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 859a0e8ed65b146e875ea95718e6173c263a063a0eb3c41a959d4b45e6a2b703 0.600000000000 1667703 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": 1181296, "vin": [ { "gen": { "height": 1181286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "859a0e8ed65b146e875ea95718e6173c263a063a0eb3c41a959d4b45e6a2b703" } } ], "extra": [ 1, 104, 109, 73, 185, 124, 176, 91, 166, 163, 199, 160, 51, 57, 30, 22, 210, 75, 170, 151, 40, 154, 26, 129, 191, 117, 41, 212, 185, 138, 61, 11, 109, 2, 17, 0, 0, 0, 3, 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