Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65ad8909f4258f2b9bcf94a0a80d1accd7a5bac596379a98239994e78be9ee89

Tx prefix hash: 1142ff0d59dd50acaeb1ebeb43a9a4119ef95735996bcf1cb2df19e3576c0742
Tx public key: 1eb90331c1f80df9328ecf3f28f246c2caad3828bd61194a8cfa16e6b8455c0a
Timestamp: 1760751263 Timestamp [UCT]: 2025-10-18 01:34:23 Age [y:d:h:m:s]: 00:033:22:47:25
Block: 1392304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24274 RingCT/type: yes/0
Extra: 011eb90331c1f80df9328ecf3f28f246c2caad3828bd61194a8cfa16e6b8455c0a0211000000052609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89a79146faa6fe71a5a171dd4c7ec46c3b92fad78670bcfb6da2e290f674a87c 0.600000000000 1880555 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": 1392314, "vin": [ { "gen": { "height": 1392304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89a79146faa6fe71a5a171dd4c7ec46c3b92fad78670bcfb6da2e290f674a87c" } } ], "extra": [ 1, 30, 185, 3, 49, 193, 248, 13, 249, 50, 142, 207, 63, 40, 242, 70, 194, 202, 173, 56, 40, 189, 97, 25, 74, 140, 250, 22, 230, 184, 69, 92, 10, 2, 17, 0, 0, 0, 5, 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