Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c0f5e9f9fe6b96abd75ecb1b78d56ee5c2995d6b9d37fc17196ea02ba27dc1

Tx prefix hash: 5ce6345d36367fb7544d49e2be9263fb47d518ac228ffaec7a6a4fd87a467cb4
Tx public key: a64deda6a204212b6f96ec47947818dcfd7004cbf7291f0ffb8d0489c701a87f
Timestamp: 1755965397 Timestamp [UCT]: 2025-08-23 16:09:57 Age [y:d:h:m:s]: 00:094:21:31:18
Block: 1352800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67769 RingCT/type: yes/0
Extra: 01a64deda6a204212b6f96ec47947818dcfd7004cbf7291f0ffb8d0489c701a87f0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c36c404e376f0ffbff6450b70acae67b16fe236494a2002f1a7136d2d52a094 0.600000000000 1840767 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": 1352810, "vin": [ { "gen": { "height": 1352800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c36c404e376f0ffbff6450b70acae67b16fe236494a2002f1a7136d2d52a094" } } ], "extra": [ 1, 166, 77, 237, 166, 162, 4, 33, 43, 111, 150, 236, 71, 148, 120, 24, 220, 253, 112, 4, 203, 247, 41, 31, 15, 251, 141, 4, 137, 199, 1, 168, 127, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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