Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4b8e8b6f7910955d668d9efce95c0d25680e683bf04a312858eaa108cf0ba79

Tx prefix hash: 9fed55a8a7af49c10ffdca82546e84d11ff45031d385e671292fe956b1e02f9d
Tx public key: ca27bc74ade3d83a1264f208628d7aaafbbd56812f9f5bd82dcb68fed1150f8e
Timestamp: 1745993506 Timestamp [UCT]: 2025-04-30 06:11:46 Age [y:d:h:m:s]: 00:194:22:32:08
Block: 1272546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137013 RingCT/type: yes/0
Extra: 01ca27bc74ade3d83a1264f208628d7aaafbbd56812f9f5bd82dcb68fed1150f8e0211000000071f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 566a7ea088f24348e4e451d7de92f612c1b21a0c0b1f3a67ee13dd8292798285 0.600000000000 1759821 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": 1272556, "vin": [ { "gen": { "height": 1272546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "566a7ea088f24348e4e451d7de92f612c1b21a0c0b1f3a67ee13dd8292798285" } } ], "extra": [ 1, 202, 39, 188, 116, 173, 227, 216, 58, 18, 100, 242, 8, 98, 141, 122, 170, 251, 189, 86, 129, 47, 159, 91, 216, 45, 203, 104, 254, 209, 21, 15, 142, 2, 17, 0, 0, 0, 7, 31, 144, 81, 122, 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