Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b5ace4ebac8a09832f307bf2ea8b1df2a94d07e04b195319298dab7aa0d442c

Tx prefix hash: 2119c591e9f8fe3a33bb9682a3a628c4844f32af3a906d2a657a0b1356f5e5a1
Tx public key: 869567d4951f183295cb74ed7b4236711970b6a6f71c8402c75987ec0cbf0f8a
Timestamp: 1763042862 Timestamp [UCT]: 2025-11-13 14:07:42 Age [y:d:h:m:s]: 00:014:16:14:48
Block: 1411273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10513 RingCT/type: yes/0
Extra: 01869567d4951f183295cb74ed7b4236711970b6a6f71c8402c75987ec0cbf0f8a021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a12a8c06ca8e2ba66ac7025fcb2e350529640802262fc0332b8721d6182de16a 0.600000000000 1899732 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": 1411283, "vin": [ { "gen": { "height": 1411273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a12a8c06ca8e2ba66ac7025fcb2e350529640802262fc0332b8721d6182de16a" } } ], "extra": [ 1, 134, 149, 103, 212, 149, 31, 24, 50, 149, 203, 116, 237, 123, 66, 54, 113, 25, 112, 182, 166, 247, 28, 132, 2, 199, 89, 135, 236, 12, 191, 15, 138, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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