Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0d91425b094e874cfd20d88a3645ecd9e0189defc9bb2e0ca74aeae5f515677

Tx prefix hash: 2f568e5c8e41a91c0b341f360ec2fbdc8051a6b8cdb7c66b9f947ef291d9f104
Tx public key: 7384b7369610ef81fbab7c9714829641c2627727ee6af3a4b67238e4078809f8
Timestamp: 1708078571 Timestamp [UCT]: 2024-02-16 10:16:11 Age [y:d:h:m:s]: 00:331:15:57:21
Block: 958713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237435 RingCT/type: yes/0
Extra: 017384b7369610ef81fbab7c9714829641c2627727ee6af3a4b67238e4078809f802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5287a918bbbc647a499c6ea364f48c2dc4b28c111dd4e1034a61aeb586d7bf82 0.600000000000 1418074 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": 958723, "vin": [ { "gen": { "height": 958713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5287a918bbbc647a499c6ea364f48c2dc4b28c111dd4e1034a61aeb586d7bf82" } } ], "extra": [ 1, 115, 132, 183, 54, 150, 16, 239, 129, 251, 171, 124, 151, 20, 130, 150, 65, 194, 98, 119, 39, 238, 106, 243, 164, 182, 114, 56, 228, 7, 136, 9, 248, 2, 17, 0, 0, 0, 4, 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