Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42e92aac459fb4efadaf8991c7a59d7dedf6572a3f011056c3240b5683b894d5

Tx prefix hash: 0c0cdfc262556b0cd35002f5a34cdcf430914753464273f5d93c8d43e84d6b1d
Tx public key: 6b72a2d8224f16e2adef7142c7ad3d99076b27819e8f645b8c5c40d951326c89
Timestamp: 1744647133 Timestamp [UCT]: 2025-04-14 16:12:13 Age [y:d:h:m:s]: 00:269:23:02:36
Block: 1261386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190739 RingCT/type: yes/0
Extra: 016b72a2d8224f16e2adef7142c7ad3d99076b27819e8f645b8c5c40d951326c89021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94c46af2e9ffc4b3770df08ba989106a40e174038b275575308a5a958520ece8 0.600000000000 1748555 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": 1261396, "vin": [ { "gen": { "height": 1261386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94c46af2e9ffc4b3770df08ba989106a40e174038b275575308a5a958520ece8" } } ], "extra": [ 1, 107, 114, 162, 216, 34, 79, 22, 226, 173, 239, 113, 66, 199, 173, 61, 153, 7, 107, 39, 129, 158, 143, 100, 91, 140, 92, 64, 217, 81, 50, 108, 137, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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