Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 278a5f5840fdf6f8946d3a910739eb300d3005392c8c9a4b74c5c7b14175cfe7

Tx prefix hash: 2c6f991bef0c150b9b6f82ac5681907ba89829f0f074bfb43381fe0346e43291
Tx public key: 35c9659a3a2662f05468b392906881c57bfe181e8f59a5556f7ec5a385d7f620
Timestamp: 1737682367 Timestamp [UCT]: 2025-01-24 01:32:47 Age [y:d:h:m:s]: 00:146:18:58:51
Block: 1203956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104629 RingCT/type: yes/0
Extra: 0135c9659a3a2662f05468b392906881c57bfe181e8f59a5556f7ec5a385d7f620021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff4af9f562e4d31e329aa9f3bb0e4ca74146ac1175c4095c9c36abe67ffc581a 0.600000000000 1690637 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": 1203966, "vin": [ { "gen": { "height": 1203956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff4af9f562e4d31e329aa9f3bb0e4ca74146ac1175c4095c9c36abe67ffc581a" } } ], "extra": [ 1, 53, 201, 101, 154, 58, 38, 98, 240, 84, 104, 179, 146, 144, 104, 129, 197, 123, 254, 24, 30, 143, 89, 165, 85, 111, 126, 197, 163, 133, 215, 246, 32, 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