Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56f9fecc5eb93e9d1c83df0ef6570981807fb1109d3f7d1a5c8afdc820b86749

Tx prefix hash: a010bb333304f6c7792f3114521d0f7924d3e1d75896dd7c9242d06693a6fabd
Tx public key: 76eddab7b12d64b49d5919b90f491aa0546e074e826939487d365583c3145d09
Timestamp: 1738303047 Timestamp [UCT]: 2025-01-31 05:57:27 Age [y:d:h:m:s]: 00:324:07:14:43
Block: 1208877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229579 RingCT/type: yes/0
Extra: 0176eddab7b12d64b49d5919b90f491aa0546e074e826939487d365583c3145d090211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a333b5ab43df2f9be94445d7e008a59c40c1c76a68c7f0be4b487fa61939e2ec 0.600000000000 1695612 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": 1208887, "vin": [ { "gen": { "height": 1208877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a333b5ab43df2f9be94445d7e008a59c40c1c76a68c7f0be4b487fa61939e2ec" } } ], "extra": [ 1, 118, 237, 218, 183, 177, 45, 100, 180, 157, 89, 25, 185, 15, 73, 26, 160, 84, 110, 7, 78, 130, 105, 57, 72, 125, 54, 85, 131, 195, 20, 93, 9, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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