Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35a04299662ce06d2c296e2d118b64c12bd988055e9bdf5cbe01a910c5e08935

Tx prefix hash: 545e2338e34e97ad8252165918c1b1164d4ed089ae9c0c2bb9ff06729377f964
Tx public key: 69a1ae28b3e606dfebfd651adc1001a3330a8c08b15221f6a5bcb426a04ad560
Timestamp: 1659291870 Timestamp [UCT]: 2022-07-31 18:24:30 Age [y:d:h:m:s]: 03:096:12:10:59
Block: 555859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 848750 RingCT/type: yes/0
Extra: 0169a1ae28b3e606dfebfd651adc1001a3330a8c08b15221f6a5bcb426a04ad5600211000000016570b1ef000000000000000000

1 output(s) for total of 8.835039767000 dcy

stealth address amount amount idx
00: d2fd4bb0525b320f63e793d346463752cd64336cb47b08a86acb98e011b57da6 8.835039767000 987775 of 0

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": 555869, "vin": [ { "gen": { "height": 555859 } } ], "vout": [ { "amount": 8835039767, "target": { "key": "d2fd4bb0525b320f63e793d346463752cd64336cb47b08a86acb98e011b57da6" } } ], "extra": [ 1, 105, 161, 174, 40, 179, 230, 6, 223, 235, 253, 101, 26, 220, 16, 1, 163, 51, 10, 140, 8, 177, 82, 33, 246, 165, 188, 180, 38, 160, 74, 213, 96, 2, 17, 0, 0, 0, 1, 101, 112, 177, 239, 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