Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 429a563bdee851562a605356493e8ec6f78496d294a510e7f0e0ab5d2db4832c

Tx prefix hash: 73cfdfd2d1422386ef5fe9254327ae3ccbc1840c464272e7ae7e814f05f79ea7
Tx public key: 8815b133af103f5eaa755d13993de2846a66cb17f8ed05d2dc9525f45772e766
Timestamp: 1759388656 Timestamp [UCT]: 2025-10-02 07:04:16 Age [y:d:h:m:s]: 00:042:21:41:42
Block: 1380984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30728 RingCT/type: yes/0
Extra: 018815b133af103f5eaa755d13993de2846a66cb17f8ed05d2dc9525f45772e766021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 764b1e480ee62451311c08b91b53f91c55206c8aa9879c254f072db907e21c3b 0.600000000000 1869095 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": 1380994, "vin": [ { "gen": { "height": 1380984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "764b1e480ee62451311c08b91b53f91c55206c8aa9879c254f072db907e21c3b" } } ], "extra": [ 1, 136, 21, 177, 51, 175, 16, 63, 94, 170, 117, 93, 19, 153, 61, 226, 132, 106, 102, 203, 23, 248, 237, 5, 210, 220, 149, 37, 244, 87, 114, 231, 102, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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