Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a069dc99f333675e0862286def83c0bad8c52d4d62ea151b15f5b88137969c9

Tx prefix hash: ecd8d86d3026ea2704c50703497223540a9452c34138d4b872c30f8c26c02ead
Tx public key: 66da43874bacc98eb1a7b6c83943f54cd63e45a098dbc023d9d5597e41fb9ed1
Timestamp: 1756480767 Timestamp [UCT]: 2025-08-29 15:19:27 Age [y:d:h:m:s]: 00:076:22:21:24
Block: 1357043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54936 RingCT/type: yes/0
Extra: 0166da43874bacc98eb1a7b6c83943f54cd63e45a098dbc023d9d5597e41fb9ed1021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 017d8888cbf09df5a705df874891f9e77445cd7c4bccb33de16b173c2054b409 0.600000000000 1845052 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": 1357053, "vin": [ { "gen": { "height": 1357043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "017d8888cbf09df5a705df874891f9e77445cd7c4bccb33de16b173c2054b409" } } ], "extra": [ 1, 102, 218, 67, 135, 75, 172, 201, 142, 177, 167, 182, 200, 57, 67, 245, 76, 214, 62, 69, 160, 152, 219, 192, 35, 217, 213, 89, 126, 65, 251, 158, 209, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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