Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6566101a23c19297842dccbef2ec5f77425b6f5d1b8415d7cf46f476a67a4bc

Tx prefix hash: 06b9ce3ec161eeb246ad0b13289bc7e8feb16672a476b8432305ee9edf456f61
Tx public key: d315b91f7b916f24d09d60bd325a11d30c73a0b9f2bdf1bf0c48468c97a401ef
Timestamp: 1705069103 Timestamp [UCT]: 2024-01-12 14:18:23 Age [y:d:h:m:s]: 01:082:19:08:17
Block: 933762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320275 RingCT/type: yes/0
Extra: 01d315b91f7b916f24d09d60bd325a11d30c73a0b9f2bdf1bf0c48468c97a401ef02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5c8024b538c088fa73e3ad8a8588379e36db5908aff78d1a6de73337125bf22 0.600000000000 1391736 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": 933772, "vin": [ { "gen": { "height": 933762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5c8024b538c088fa73e3ad8a8588379e36db5908aff78d1a6de73337125bf22" } } ], "extra": [ 1, 211, 21, 185, 31, 123, 145, 111, 36, 208, 157, 96, 189, 50, 90, 17, 211, 12, 115, 160, 185, 242, 189, 241, 191, 12, 72, 70, 140, 151, 164, 1, 239, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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