Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b25e43bb8314ed3d15ffd1e503ffdd375e50df1853631bf07a090a69867bb24

Tx prefix hash: 522fd1d674fa0080404c1bdf9871a39927211e4c35ce0e1ed973d6308a2fc04b
Tx public key: 69e2f73ba11dc73ccf289a85e5c666a57ecbf3d3296ef7bfd50d894fe02e706d
Timestamp: 1728179136 Timestamp [UCT]: 2024-10-06 01:45:36 Age [y:d:h:m:s]: 00:180:09:57:25
Block: 1125366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128730 RingCT/type: yes/0
Extra: 0169e2f73ba11dc73ccf289a85e5c666a57ecbf3d3296ef7bfd50d894fe02e706d02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 306f5c6bee3a686f626cb6f8ebe8a14af20e9d025c2c02530500a46e59462a34 0.600000000000 1608047 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": 1125376, "vin": [ { "gen": { "height": 1125366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "306f5c6bee3a686f626cb6f8ebe8a14af20e9d025c2c02530500a46e59462a34" } } ], "extra": [ 1, 105, 226, 247, 59, 161, 29, 199, 60, 207, 40, 154, 133, 229, 198, 102, 165, 126, 203, 243, 211, 41, 110, 247, 191, 213, 13, 137, 79, 224, 46, 112, 109, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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