Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a30fae09c4a88c50f492bbd05a8a752a3132f485103e46717ac5a7009a1449e1

Tx prefix hash: c1e427fb84bc6406427072251749f531b1a2b0dc63c80715159f09629de248c8
Tx public key: 3a1e89ba91976e8c1614329dae5f1f34f8927a1bac725649d7e94a70ecfbe5aa
Timestamp: 1753943090 Timestamp [UCT]: 2025-07-31 06:24:50 Age [y:d:h:m:s]: 00:080:13:23:44
Block: 1337149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56413 RingCT/type: yes/0
Extra: 013a1e89ba91976e8c1614329dae5f1f34f8927a1bac725649d7e94a70ecfbe5aa021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 948ebc28ba1a802e1ca193bfbb2f26fab14c89751a4463780280b161d1d1a9c5 0.600000000000 1824952 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": 1337159, "vin": [ { "gen": { "height": 1337149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "948ebc28ba1a802e1ca193bfbb2f26fab14c89751a4463780280b161d1d1a9c5" } } ], "extra": [ 1, 58, 30, 137, 186, 145, 151, 110, 140, 22, 20, 50, 157, 174, 95, 31, 52, 248, 146, 122, 27, 172, 114, 86, 73, 215, 233, 74, 112, 236, 251, 229, 170, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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