Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1b12b715011801ef12b568fc453c5a287f15b3cb8baa38d2a98ea3043f097fe

Tx prefix hash: 29390268f5fd8af81ad02cdaa906992ce7ac39c99ffc7e561d0a0b3dd2cde0c7
Tx public key: 9afbd478c08ca709a32a97e9d5ca15c90f6d870e7bd1293140bbe5a9a299d830
Timestamp: 1733051491 Timestamp [UCT]: 2024-12-01 11:11:31 Age [y:d:h:m:s]: 00:166:08:39:51
Block: 1165662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118722 RingCT/type: yes/0
Extra: 019afbd478c08ca709a32a97e9d5ca15c90f6d870e7bd1293140bbe5a9a299d8300211000000018f9f0b94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c7565d0392cb45027c24c160eb776ba95987f416cb253f1906ebc154b2ae5e0 0.600000000000 1651337 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": 1165672, "vin": [ { "gen": { "height": 1165662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c7565d0392cb45027c24c160eb776ba95987f416cb253f1906ebc154b2ae5e0" } } ], "extra": [ 1, 154, 251, 212, 120, 192, 140, 167, 9, 163, 42, 151, 233, 213, 202, 21, 201, 15, 109, 135, 14, 123, 209, 41, 49, 64, 187, 229, 169, 162, 153, 216, 48, 2, 17, 0, 0, 0, 1, 143, 159, 11, 148, 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