Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15b44dd891d6d170d9203ad4fb6ea338f973a20c07a7cf050de211211ec71237

Tx prefix hash: 4dc53cfcaf64e071655a57fd0e3c4e3dfd1d10aad7bef6a758f1e3787240402c
Tx public key: a652d27964fbb233d3c0f3a0b9b6a502159f2120be1999af3a853ea486b8e536
Timestamp: 1703973152 Timestamp [UCT]: 2023-12-30 21:52:32 Age [y:d:h:m:s]: 01:174:05:06:45
Block: 924677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385484 RingCT/type: yes/0
Extra: 01a652d27964fbb233d3c0f3a0b9b6a502159f2120be1999af3a853ea486b8e53602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6998996cc582c67442547453968e0907a7da0e979f9ea27975c45e185bb9a6c 0.600000000000 1382433 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": 924687, "vin": [ { "gen": { "height": 924677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6998996cc582c67442547453968e0907a7da0e979f9ea27975c45e185bb9a6c" } } ], "extra": [ 1, 166, 82, 210, 121, 100, 251, 178, 51, 211, 192, 243, 160, 185, 182, 165, 2, 21, 159, 33, 32, 190, 25, 153, 175, 58, 133, 62, 164, 134, 184, 229, 54, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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