Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88f0e2583cf840a71b3d10a33dfe175be9fa6d5e316938ee3dca226a613737ef

Tx prefix hash: dec016050697d1b8cb0f8a97ad1399b5d6231494c21cafa9010d4115824a25e1
Tx public key: f84b2abcf0bb6abde03a32f61fe7d10c2c58c968d4ae169036575fd3a2f6eace
Timestamp: 1730354458 Timestamp [UCT]: 2024-10-31 06:00:58 Age [y:d:h:m:s]: 00:148:18:21:48
Block: 1143323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106153 RingCT/type: yes/0
Extra: 01f84b2abcf0bb6abde03a32f61fe7d10c2c58c968d4ae169036575fd3a2f6eace0211000000072609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c6aff9f810404d412c5088745745fc18f000d298ce7232baf8a4920f4932b57 0.600000000000 1627186 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": 1143333, "vin": [ { "gen": { "height": 1143323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c6aff9f810404d412c5088745745fc18f000d298ce7232baf8a4920f4932b57" } } ], "extra": [ 1, 248, 75, 42, 188, 240, 187, 106, 189, 224, 58, 50, 246, 31, 231, 209, 12, 44, 88, 201, 104, 212, 174, 22, 144, 54, 87, 95, 211, 162, 246, 234, 206, 2, 17, 0, 0, 0, 7, 38, 9, 179, 160, 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