Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7456c0382222783feb4699a82dd591881015110ad19f0d5856ad3e8916dc9a0f

Tx prefix hash: 777a72841c879f158ab98dd81ac0969bfcdc2ab5eaf774cd8e8929a98c989540
Tx public key: a2fea5f41dc40ed1196394d60743e73b1b7d3c5fb38d212c2a5ad889c70e89eb
Timestamp: 1744676886 Timestamp [UCT]: 2025-04-15 00:28:06 Age [y:d:h:m:s]: 00:225:13:56:11
Block: 1261628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158963 RingCT/type: yes/0
Extra: 01a2fea5f41dc40ed1196394d60743e73b1b7d3c5fb38d212c2a5ad889c70e89eb02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 639497c740b33770b498073eab450a8adf0f37ae77cc4d4d919eb33ae32d0afd 0.600000000000 1748801 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": 1261638, "vin": [ { "gen": { "height": 1261628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "639497c740b33770b498073eab450a8adf0f37ae77cc4d4d919eb33ae32d0afd" } } ], "extra": [ 1, 162, 254, 165, 244, 29, 196, 14, 209, 25, 99, 148, 214, 7, 67, 231, 59, 27, 125, 60, 95, 179, 141, 33, 44, 42, 90, 216, 137, 199, 14, 137, 235, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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