Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9c1bd05ae505d5515dda29ce86d9d69e2ae40f9e73cc950af8e9198ed252b9f

Tx prefix hash: 9c8e36e6c3348d5ced604db256a894b8d980b12e4536154bd32bed59f8222684
Tx public key: 344f80e4d0e9785afe0377424841957cbf0d1b631e99a496e7dba3d3ecb59f03
Timestamp: 1748060195 Timestamp [UCT]: 2025-05-24 04:16:35 Age [y:d:h:m:s]: 00:169:17:48:40
Block: 1289661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118996 RingCT/type: yes/0
Extra: 01344f80e4d0e9785afe0377424841957cbf0d1b631e99a496e7dba3d3ecb59f030211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0181871a4aeb2c3af1e12e7547853c5e41d1fb0ddb5648c771dfdfd2912b273 0.600000000000 1777130 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": 1289671, "vin": [ { "gen": { "height": 1289661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0181871a4aeb2c3af1e12e7547853c5e41d1fb0ddb5648c771dfdfd2912b273" } } ], "extra": [ 1, 52, 79, 128, 228, 208, 233, 120, 90, 254, 3, 119, 66, 72, 65, 149, 124, 191, 13, 27, 99, 30, 153, 164, 150, 231, 219, 163, 211, 236, 181, 159, 3, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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