Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d119535c0dcd923c1376064582907f1e94ce106fe350ea9f28b3714c7472b159

Tx prefix hash: 7de595fa8d57ffdecde5386844e0d41a6f00c7ba3d9aeb1ff915884be66f6552
Tx public key: a6ec8dc7c4df863eff593d3d8d985592498494dd38e1c554c3c4d8e1de5a1660
Timestamp: 1736509592 Timestamp [UCT]: 2025-01-10 11:46:32 Age [y:d:h:m:s]: 00:065:23:30:27
Block: 1194291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46947 RingCT/type: yes/0
Extra: 01a6ec8dc7c4df863eff593d3d8d985592498494dd38e1c554c3c4d8e1de5a1660021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38f808e8067c10e86c975a130c3c57db2b62d353f7f017b12af95d87518a45be 0.600000000000 1680860 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": 1194301, "vin": [ { "gen": { "height": 1194291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38f808e8067c10e86c975a130c3c57db2b62d353f7f017b12af95d87518a45be" } } ], "extra": [ 1, 166, 236, 141, 199, 196, 223, 134, 62, 255, 89, 61, 61, 141, 152, 85, 146, 73, 132, 148, 221, 56, 225, 197, 84, 195, 196, 216, 225, 222, 90, 22, 96, 2, 17, 0, 0, 0, 1, 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