Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8cb057d4bbede5c8a3a2e377f530429d54c3f2c6b8e23afca8c4ee09db86951

Tx prefix hash: 0c997d2957813131be0b5ee30db319fd8308c08654fe2b4ff83f58e73892f611
Tx public key: 2d3d35b47d85ef8b07475d97eecc472ff61a8159aa4248f66a6fb39af3fb6c82
Timestamp: 1696939112 Timestamp [UCT]: 2023-10-10 11:58:32 Age [y:d:h:m:s]: 01:090:03:51:29
Block: 866578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325687 RingCT/type: yes/0
Extra: 012d3d35b47d85ef8b07475d97eecc472ff61a8159aa4248f66a6fb39af3fb6c82021100000001faf35c9c000000000000000000

1 output(s) for total of 0.825405550000 dcy

stealth address amount amount idx
00: eb9e9c7158f0b3507a22651b4205a456d7887910daef2f3b65ae2568f7f5ef7a 0.825405550000 1321188 of 0

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": 866588, "vin": [ { "gen": { "height": 866578 } } ], "vout": [ { "amount": 825405550, "target": { "key": "eb9e9c7158f0b3507a22651b4205a456d7887910daef2f3b65ae2568f7f5ef7a" } } ], "extra": [ 1, 45, 61, 53, 180, 125, 133, 239, 139, 7, 71, 93, 151, 238, 204, 71, 47, 246, 26, 129, 89, 170, 66, 72, 246, 106, 111, 179, 154, 243, 251, 108, 130, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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