Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb3a58cfcec7933dbf901f9b2ee0b9cecfa734ca37c113f58e3c0b54103ca8d8

Tx prefix hash: d70f2558d06b468b4c2b3b69b3c19718205ef32e107a6dabc68d19292619ddc5
Tx public key: b8aed5bd64944ceb129a7cb0efc181abbf84374730fe8e6325de1dc4af3f11ce
Timestamp: 1735306857 Timestamp [UCT]: 2024-12-27 13:40:57 Age [y:d:h:m:s]: 00:093:23:42:05
Block: 1184327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66961 RingCT/type: yes/0
Extra: 01b8aed5bd64944ceb129a7cb0efc181abbf84374730fe8e6325de1dc4af3f11ce0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b640671abf781f687f70e007ff7f07838abd495c01c7342f2c2e3347ddcd0608 0.600000000000 1670784 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": 1184337, "vin": [ { "gen": { "height": 1184327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b640671abf781f687f70e007ff7f07838abd495c01c7342f2c2e3347ddcd0608" } } ], "extra": [ 1, 184, 174, 213, 189, 100, 148, 76, 235, 18, 154, 124, 176, 239, 193, 129, 171, 191, 132, 55, 71, 48, 254, 142, 99, 37, 222, 29, 196, 175, 63, 17, 206, 2, 17, 0, 0, 0, 7, 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