Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fa8acccd3b2ac241b6b920b4b62e14d5caec1b66609b93c11ce64d06de60cf8

Tx prefix hash: f31ecec0eb71c883f6465cc33f8c7eda0684763200f819781f6d2decec1aca2b
Tx public key: c0dea615fa0a3ed0e1b4d1c7a27e6826c9eb021992fcbc69b4be544bbbf335f6
Timestamp: 1726002003 Timestamp [UCT]: 2024-09-10 21:00:03 Age [y:d:h:m:s]: 00:212:06:03:29
Block: 1107318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151538 RingCT/type: yes/0
Extra: 01c0dea615fa0a3ed0e1b4d1c7a27e6826c9eb021992fcbc69b4be544bbbf335f6021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 992539214e6ce148325861430cbf35dd9f8a09ebc44bd7c2275efcb7c23b4c08 0.600000000000 1584929 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": 1107328, "vin": [ { "gen": { "height": 1107318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "992539214e6ce148325861430cbf35dd9f8a09ebc44bd7c2275efcb7c23b4c08" } } ], "extra": [ 1, 192, 222, 166, 21, 250, 10, 62, 208, 225, 180, 209, 199, 162, 126, 104, 38, 201, 235, 2, 25, 146, 252, 188, 105, 180, 190, 84, 75, 187, 243, 53, 246, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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