Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b81d7d31a4644c2b341b1634a07df769720ac2fc0c5451d4942c3347b02a855

Tx prefix hash: f3244ffc16180a04d7e28f0307ac99f689fb39162bde5bf03857ade869c08567
Tx public key: ab837ba067d05df23b1fdb8affd5eb7c15d3d2bd6063e72fb946a442942424f8
Timestamp: 1736089682 Timestamp [UCT]: 2025-01-05 15:08:02 Age [y:d:h:m:s]: 00:073:07:05:04
Block: 1190818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52177 RingCT/type: yes/0
Extra: 01ab837ba067d05df23b1fdb8affd5eb7c15d3d2bd6063e72fb946a442942424f802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1d89c57a6af5a0774e30a39469ad23329f68b215e356335f06ae96b2a9c052d 0.600000000000 1677337 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": 1190828, "vin": [ { "gen": { "height": 1190818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1d89c57a6af5a0774e30a39469ad23329f68b215e356335f06ae96b2a9c052d" } } ], "extra": [ 1, 171, 131, 123, 160, 103, 208, 93, 242, 59, 31, 219, 138, 255, 213, 235, 124, 21, 211, 210, 189, 96, 99, 231, 47, 185, 70, 164, 66, 148, 36, 36, 248, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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