Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b429d324b7738ee339921d1cd8395248bbe02b8b3a37fd0742ec9798d6e4de79

Tx prefix hash: 91b950e2bbe300bcbfa2bd821a6281c034de097eb503dfc7371719f669a4b167
Tx public key: 0433235caa5c94d9836c6a1c78b567461cec87d9708fb49bb7af3385ae5b1a4e
Timestamp: 1730142068 Timestamp [UCT]: 2024-10-28 19:01:08 Age [y:d:h:m:s]: 00:027:00:22:59
Block: 1141566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19325 RingCT/type: yes/0
Extra: 010433235caa5c94d9836c6a1c78b567461cec87d9708fb49bb7af3385ae5b1a4e0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 017442d1243e0cfe5098c71674bb1c7fbaf68dc591f01b91c8d657c09201b831 0.600000000000 1625373 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": 1141576, "vin": [ { "gen": { "height": 1141566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "017442d1243e0cfe5098c71674bb1c7fbaf68dc591f01b91c8d657c09201b831" } } ], "extra": [ 1, 4, 51, 35, 92, 170, 92, 148, 217, 131, 108, 106, 28, 120, 181, 103, 70, 28, 236, 135, 217, 112, 143, 180, 155, 183, 175, 51, 133, 174, 91, 26, 78, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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