Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dca7fc36b959af16d899de31f834feb3f755c99bb21bb44519f193f853e3c2fb

Tx prefix hash: 6dc0c150e052d069ef64372a3306cb1bee559d4a03aec8e93a98a4b71d0dbfbf
Tx public key: 35b4d3911942896781660d272a4e0c3f92b08d97157813396ad5adbbe437a2a0
Timestamp: 1737773084 Timestamp [UCT]: 2025-01-25 02:44:44 Age [y:d:h:m:s]: 00:326:17:07:45
Block: 1204705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231079 RingCT/type: yes/0
Extra: 0135b4d3911942896781660d272a4e0c3f92b08d97157813396ad5adbbe437a2a0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 594eb7a34c4e91c176c4f5ea5e9ec80ce54f0949af2603e6b0b046edf3729a65 0.600000000000 1691396 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": 1204715, "vin": [ { "gen": { "height": 1204705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "594eb7a34c4e91c176c4f5ea5e9ec80ce54f0949af2603e6b0b046edf3729a65" } } ], "extra": [ 1, 53, 180, 211, 145, 25, 66, 137, 103, 129, 102, 13, 39, 42, 78, 12, 63, 146, 176, 141, 151, 21, 120, 19, 57, 106, 213, 173, 187, 228, 55, 162, 160, 2, 17, 0, 0, 0, 2, 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