Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79c66e76ec2bcebc50aab5dfbebc5d6d85d3bdde1493c587c63993990e43dc55

Tx prefix hash: 8d6811c81b3cf4ed8453b3df88b258c967ccc21cb3dd760d74f3d1062edb9030
Tx public key: 9242910c0f9f0c97fe8337bd57cb173e55188ebbedb2e2888a49cdeadd76e536
Timestamp: 1725092912 Timestamp [UCT]: 2024-08-31 08:28:32 Age [y:d:h:m:s]: 00:084:22:32:10
Block: 1099774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60744 RingCT/type: yes/0
Extra: 019242910c0f9f0c97fe8337bd57cb173e55188ebbedb2e2888a49cdeadd76e53602110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00fca3b0ff4510eaeec7b57df0c7e3eb530da282ab86690d92ee2cdbe38e2cb4 0.600000000000 1575743 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": 1099784, "vin": [ { "gen": { "height": 1099774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00fca3b0ff4510eaeec7b57df0c7e3eb530da282ab86690d92ee2cdbe38e2cb4" } } ], "extra": [ 1, 146, 66, 145, 12, 15, 159, 12, 151, 254, 131, 55, 189, 87, 203, 23, 62, 85, 24, 142, 187, 237, 178, 226, 136, 138, 73, 205, 234, 221, 118, 229, 54, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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