Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16fb702c0d81821094c32948c5f782aa47d107abbbe21e9a7cd174ce2894c088

Tx prefix hash: 19ba764af70a40075b7aa6bc3e564de7d0f7ff1f23663c65c8476f83be0514df
Tx public key: 8a77a561c1d066f08b2f1617c01775f3a54980552c72709509c5d1f8966f4148
Timestamp: 1718174062 Timestamp [UCT]: 2024-06-12 06:34:22 Age [y:d:h:m:s]: 00:300:17:03:36
Block: 1042426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214882 RingCT/type: yes/0
Extra: 018a77a561c1d066f08b2f1617c01775f3a54980552c72709509c5d1f8966f414802110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64b9a85cd080ab32196b0b3cacc8d764bd021362bdc2b2b2a8abbc41774e3a06 0.600000000000 1511343 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": 1042436, "vin": [ { "gen": { "height": 1042426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64b9a85cd080ab32196b0b3cacc8d764bd021362bdc2b2b2a8abbc41774e3a06" } } ], "extra": [ 1, 138, 119, 165, 97, 193, 208, 102, 240, 139, 47, 22, 23, 192, 23, 117, 243, 165, 73, 128, 85, 44, 114, 112, 149, 9, 197, 209, 248, 150, 111, 65, 72, 2, 17, 0, 0, 0, 8, 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