Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 156a8e4266f5ff840b5cc74120b581b7b622ab4c172b7459e07777431914e8bf

Tx prefix hash: 22d05f2346d9613a8d00904f98352b307ebd30e1c358d13b13f5ac5a636f35b7
Tx public key: b44a7eae2eff7087ebb62fd208814f98d3c2f3ce3761b5d77be77f1055a231e5
Timestamp: 1754106520 Timestamp [UCT]: 2025-08-02 03:48:40 Age [y:d:h:m:s]: 00:106:05:05:20
Block: 1338477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74789 RingCT/type: yes/0
Extra: 01b44a7eae2eff7087ebb62fd208814f98d3c2f3ce3761b5d77be77f1055a231e5021100000007ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e143ef8e5167bb8808531b91396a3ec40fb5c0e30b4bb7655939acc026be337 0.600000000000 1826286 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": 1338487, "vin": [ { "gen": { "height": 1338477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e143ef8e5167bb8808531b91396a3ec40fb5c0e30b4bb7655939acc026be337" } } ], "extra": [ 1, 180, 74, 126, 174, 46, 255, 112, 135, 235, 182, 47, 210, 8, 129, 79, 152, 211, 194, 243, 206, 55, 97, 181, 215, 123, 231, 127, 16, 85, 162, 49, 229, 2, 17, 0, 0, 0, 7, 173, 121, 72, 208, 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