Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3920d78e0c86a7434d89b96ca674ae779f579cba9a0d5b1ae3ce9a81b4659ff

Tx prefix hash: ae769af7c52c840465d4888b81a31a2b5ad105442aae32822aa856555db18a83
Tx public key: e4a2036aad2461a2487a288e3d49f20d120ce8b73d73c21ee46bc13172c55f50
Timestamp: 1580480780 Timestamp [UCT]: 2020-01-31 14:26:20 Age [y:d:h:m:s]: 04:333:05:56:45
Block: 55827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129413 RingCT/type: yes/0
Extra: 01e4a2036aad2461a2487a288e3d49f20d120ce8b73d73c21ee46bc13172c55f5002110000000217786bcf000000000000000000

1 output(s) for total of 400.887761923000 dcy

stealth address amount amount idx
00: 666ccadd859cdcf1749de1c95d526297291266e5313fdd7abfc5a3c957a02b9e 400.887761923000 103010 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": 55837, "vin": [ { "gen": { "height": 55827 } } ], "vout": [ { "amount": 400887761923, "target": { "key": "666ccadd859cdcf1749de1c95d526297291266e5313fdd7abfc5a3c957a02b9e" } } ], "extra": [ 1, 228, 162, 3, 106, 173, 36, 97, 162, 72, 122, 40, 142, 61, 73, 242, 13, 18, 12, 232, 183, 61, 115, 194, 30, 228, 107, 193, 49, 114, 197, 95, 80, 2, 17, 0, 0, 0, 2, 23, 120, 107, 207, 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