Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fc4247dcd533c3ed57cda053108c3dc114b63369978452579c64f49053027cc

Tx prefix hash: 55b75cf758a19a8de403002b4103fc7c22e137fdb0c5126c50525c2c41de7470
Tx public key: 82d3408d8d0e3e2a11c7d3061693cd778ce663d781a2d82d0304dac02804c08a
Timestamp: 1706406631 Timestamp [UCT]: 2024-01-28 01:50:31 Age [y:d:h:m:s]: 01:143:10:32:32
Block: 944834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363514 RingCT/type: yes/0
Extra: 0182d3408d8d0e3e2a11c7d3061693cd778ce663d781a2d82d0304dac02804c08a02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 072db88efb0722f23203607215ccea098b5e0750973ff0387ffffd501e46a9e7 0.600000000000 1403120 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": 944844, "vin": [ { "gen": { "height": 944834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "072db88efb0722f23203607215ccea098b5e0750973ff0387ffffd501e46a9e7" } } ], "extra": [ 1, 130, 211, 64, 141, 141, 14, 62, 42, 17, 199, 211, 6, 22, 147, 205, 119, 140, 230, 99, 215, 129, 162, 216, 45, 3, 4, 218, 192, 40, 4, 192, 138, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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