Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bb9479b4913eb38fb3ff687271f93c692e97b4ff01f36d14bd7fcdb9766c9ef

Tx prefix hash: 2471b4f3002c6a5bc6016b40232d9f097b47b3453cdd119c2ed46221e940b41d
Tx public key: 68419685a613aae5317e8a2168188777fd8ba5706c33c6711c0be92cd2c343e5
Timestamp: 1736789877 Timestamp [UCT]: 2025-01-13 17:37:57 Age [y:d:h:m:s]: 00:343:04:51:36
Block: 1196613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242830 RingCT/type: yes/0
Extra: 0168419685a613aae5317e8a2168188777fd8ba5706c33c6711c0be92cd2c343e50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12ffc3cbdf0a3640ea020e62162049d926d0d6ca82779e0ebd18025cd2c19a7f 0.600000000000 1683214 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": 1196623, "vin": [ { "gen": { "height": 1196613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12ffc3cbdf0a3640ea020e62162049d926d0d6ca82779e0ebd18025cd2c19a7f" } } ], "extra": [ 1, 104, 65, 150, 133, 166, 19, 170, 229, 49, 126, 138, 33, 104, 24, 135, 119, 253, 139, 165, 112, 108, 51, 198, 113, 28, 11, 233, 44, 210, 195, 67, 229, 2, 17, 0, 0, 0, 2, 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