Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3360cf559cb00c3cdcdeef2172fd6175686ebb754799a35e1e19b5c2c7fdc555

Tx prefix hash: 96f1cdd447c0376cdf4af7fa09c7dc4354684abc1dab5c6275ee4ec8a6fd84e1
Tx public key: 6a0e2f82880afc821500d5a2396134e530a0d3caefaa31ef256affddab6ebdb0
Timestamp: 1736598054 Timestamp [UCT]: 2025-01-11 12:20:54 Age [y:d:h:m:s]: 00:081:08:46:02
Block: 1195016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57925 RingCT/type: yes/0
Extra: 016a0e2f82880afc821500d5a2396134e530a0d3caefaa31ef256affddab6ebdb00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24354090b0be39f1e2bb7d91b49a1f054a5d2dd33f8463c9fdc652207d9e307a 0.600000000000 1681601 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": 1195026, "vin": [ { "gen": { "height": 1195016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24354090b0be39f1e2bb7d91b49a1f054a5d2dd33f8463c9fdc652207d9e307a" } } ], "extra": [ 1, 106, 14, 47, 130, 136, 10, 252, 130, 21, 0, 213, 162, 57, 97, 52, 229, 48, 160, 211, 202, 239, 170, 49, 239, 37, 106, 255, 221, 171, 110, 189, 176, 2, 17, 0, 0, 0, 3, 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