Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 152339c20bc0237ca15479451f0639233d74dbfdca509d5e9ecb28bc4f97a288

Tx prefix hash: 63845f4bed6c76af8c15ea1fafb9253c1fa410f359e80cee38d840c260d4296a
Tx public key: 3721910afa2c7160b035e6c833309a16063c70b2ccede4840f9cb1f171c1d59d
Timestamp: 1732502285 Timestamp [UCT]: 2024-11-25 02:38:05 Age [y:d:h:m:s]: 00:167:08:03:26
Block: 1161109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119430 RingCT/type: yes/0
Extra: 013721910afa2c7160b035e6c833309a16063c70b2ccede4840f9cb1f171c1d59d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9305a4fafc430f12821a043fdfb61c2b109f625ae4b195f8745b3ff2e6b26b80 0.600000000000 1646760 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": 1161119, "vin": [ { "gen": { "height": 1161109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9305a4fafc430f12821a043fdfb61c2b109f625ae4b195f8745b3ff2e6b26b80" } } ], "extra": [ 1, 55, 33, 145, 10, 250, 44, 113, 96, 176, 53, 230, 200, 51, 48, 154, 22, 6, 60, 112, 178, 204, 237, 228, 132, 15, 156, 177, 241, 113, 193, 213, 157, 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