Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c5a1943c91244087a78212ab9ced180222ba6dae4976ec84e7f5efdde8e391f

Tx prefix hash: 6729a752b72caea2324760ec5a153ba30b6bd2048b0be4693971ef181296fd6a
Tx public key: 38325b059e75f77d8767187104536ed4d7c4b7c78c6ea29ffc40def1be3f5cf4
Timestamp: 1737340589 Timestamp [UCT]: 2025-01-20 02:36:29 Age [y:d:h:m:s]: 00:302:21:41:37
Block: 1201118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214047 RingCT/type: yes/0
Extra: 0138325b059e75f77d8767187104536ed4d7c4b7c78c6ea29ffc40def1be3f5cf40211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50930df3adba9b4a56288c7e3576fba479d755f6af49e59d822f3fb9f9b194bf 0.600000000000 1687767 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": 1201128, "vin": [ { "gen": { "height": 1201118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50930df3adba9b4a56288c7e3576fba479d755f6af49e59d822f3fb9f9b194bf" } } ], "extra": [ 1, 56, 50, 91, 5, 158, 117, 247, 125, 135, 103, 24, 113, 4, 83, 110, 212, 215, 196, 183, 199, 140, 110, 162, 159, 252, 64, 222, 241, 190, 63, 92, 244, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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