Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 295c126686977bb9821c8494122495e21acc2a980aebc15ea6d5848ea9412a5c

Tx prefix hash: e2c9a8598251f0ccedb62c2a4c560178fbb33e95e54df61e17a36aed705835b5
Tx public key: 0f0dd2c6f0915aaf10ebcb37bddcf5a1660237d8034e101e47bcaede4e1c5a4e
Timestamp: 1706963502 Timestamp [UCT]: 2024-02-03 12:31:42 Age [y:d:h:m:s]: 01:279:07:38:56
Block: 949466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458407 RingCT/type: yes/0
Extra: 010f0dd2c6f0915aaf10ebcb37bddcf5a1660237d8034e101e47bcaede4e1c5a4e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0da47563440646dd60973ba03a01a24adb8ac4d5ac124be895936a9f9b363b8a 0.600000000000 1407992 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": 949476, "vin": [ { "gen": { "height": 949466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0da47563440646dd60973ba03a01a24adb8ac4d5ac124be895936a9f9b363b8a" } } ], "extra": [ 1, 15, 13, 210, 198, 240, 145, 90, 175, 16, 235, 203, 55, 189, 220, 245, 161, 102, 2, 55, 216, 3, 78, 16, 30, 71, 188, 174, 222, 78, 28, 90, 78, 2, 17, 0, 0, 0, 2, 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