Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91bf2a53992c75f5e138dca3916775ade43f68ef1e9320f5e12f3ac41c5f142b

Tx prefix hash: 5966e89c9bf23b2b3a193dec1b7940df835215928bf5e243a9d5d0ffdfd7b356
Tx public key: 0b0e41a41c53ff967d47f7c89abf06a63a1f06d987cc892351e52894104eacd4
Timestamp: 1762533219 Timestamp [UCT]: 2025-11-07 16:33:39 Age [y:d:h:m:s]: 00:046:06:15:53
Block: 1407053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33111 RingCT/type: yes/0
Extra: 010b0e41a41c53ff967d47f7c89abf06a63a1f06d987cc892351e52894104eacd402110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff0c9d7c3a3713887e180a63a45469dfb29338d041e1d9fe4c1522219bd731f5 0.600000000000 1895460 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": 1407063, "vin": [ { "gen": { "height": 1407053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff0c9d7c3a3713887e180a63a45469dfb29338d041e1d9fe4c1522219bd731f5" } } ], "extra": [ 1, 11, 14, 65, 164, 28, 83, 255, 150, 125, 71, 247, 200, 154, 191, 6, 166, 58, 31, 6, 217, 135, 204, 137, 35, 81, 229, 40, 148, 16, 78, 172, 212, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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