Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a4a26159635fbcd92580adfeed80aa6454d278a88e80de9a31c4933a18121ea

Tx prefix hash: 7f0b56398ba5fc669aba4b7e8b93a05c2794c3ef6157a25f81193f27ea6cb086
Tx public key: 1c464fc2c71a19de27ccbbf4f845d352f2054afe91e1169cf5f26738f72a23f3
Timestamp: 1764500022 Timestamp [UCT]: 2025-11-30 10:53:42 Age [y:d:h:m:s]: 00:000:05:56:57
Block: 1423357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173 RingCT/type: yes/0
Extra: 011c464fc2c71a19de27ccbbf4f845d352f2054afe91e1169cf5f26738f72a23f3021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8240f89d6b6a5c742c010cd12763d0f57d3a9ca9d27feb4118fe9f09681659a3 0.600000000000 1911964 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": 1423367, "vin": [ { "gen": { "height": 1423357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8240f89d6b6a5c742c010cd12763d0f57d3a9ca9d27feb4118fe9f09681659a3" } } ], "extra": [ 1, 28, 70, 79, 194, 199, 26, 25, 222, 39, 204, 187, 244, 248, 69, 211, 82, 242, 5, 74, 254, 145, 225, 22, 156, 245, 242, 103, 56, 247, 42, 35, 243, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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