Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 227fb4b714bd7d1a65d37eaa1166f359bc895f64bafa495448df3f41d833af34

Tx prefix hash: 0d4f808b89d5b633e019ed9b3aed79490c49ca461c602f21a6da77b0cfd3fce7
Tx public key: c0b85317e01aa7c7bae37b1cdc23b6016ee0f226d5f2ed6554f8a94bd28e3a9e
Timestamp: 1736905958 Timestamp [UCT]: 2025-01-15 01:52:38 Age [y:d:h:m:s]: 00:153:16:30:47
Block: 1197560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109554 RingCT/type: yes/0
Extra: 01c0b85317e01aa7c7bae37b1cdc23b6016ee0f226d5f2ed6554f8a94bd28e3a9e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf9e940eb832c125d4eee89fc6305bd6ac04c2b4eae262a0842f96da736fd69d 0.600000000000 1684173 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": 1197570, "vin": [ { "gen": { "height": 1197560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf9e940eb832c125d4eee89fc6305bd6ac04c2b4eae262a0842f96da736fd69d" } } ], "extra": [ 1, 192, 184, 83, 23, 224, 26, 167, 199, 186, 227, 123, 28, 220, 35, 182, 1, 110, 224, 242, 38, 213, 242, 237, 101, 84, 248, 169, 75, 210, 142, 58, 158, 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