Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1617aadf2826b2d0209ded4690e2fa5db0ad763c0cc1228c1e40ea1a28fd13c

Tx prefix hash: 693a400c7cdcc9c2939778cae8cfec9410dfc3b5dc287476a744a546ec4a98a4
Tx public key: 5435c1b86ac307d40643d3d6163d498bdc59af49f1fda0b5c753dd439f1ea7bf
Timestamp: 1735200571 Timestamp [UCT]: 2024-12-26 08:09:31 Age [y:d:h:m:s]: 00:103:11:18:18
Block: 1183459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73722 RingCT/type: yes/0
Extra: 015435c1b86ac307d40643d3d6163d498bdc59af49f1fda0b5c753dd439f1ea7bf021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c288758ef87e6ad659d66caedf581f09877dcc62e2b1e612fa46716519dc52df 0.600000000000 1669904 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": 1183469, "vin": [ { "gen": { "height": 1183459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c288758ef87e6ad659d66caedf581f09877dcc62e2b1e612fa46716519dc52df" } } ], "extra": [ 1, 84, 53, 193, 184, 106, 195, 7, 212, 6, 67, 211, 214, 22, 61, 73, 139, 220, 89, 175, 73, 241, 253, 160, 181, 199, 83, 221, 67, 159, 30, 167, 191, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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