Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afc09973a55936f3450464bcd064db61ee804fcec69b244e91df8e64a85ed24b

Tx prefix hash: cd3d095c2df810217455a5fcee06f5538966caab85c431979c38f1eb7b1b5392
Tx public key: f1b1b933508910a3df3eacaca962309ed857f86c7da3640ed0dd5b2248179871
Timestamp: 1577734205 Timestamp [UCT]: 2019-12-30 19:30:05 Age [y:d:h:m:s]: 05:075:17:08:04
Block: 35274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203858 RingCT/type: yes/0
Extra: 01f1b1b933508910a3df3eacaca962309ed857f86c7da3640ed0dd5b22481798710211000000084943cd9f000000000000000000

1 output(s) for total of 468.967642821000 dcy

stealth address amount amount idx
00: 3d3f9aa1ccc8cddd7e5ff854cfdc52be4b1cbc59bb938ee2b40d30736c7cbe47 468.967642821000 59404 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": 35284, "vin": [ { "gen": { "height": 35274 } } ], "vout": [ { "amount": 468967642821, "target": { "key": "3d3f9aa1ccc8cddd7e5ff854cfdc52be4b1cbc59bb938ee2b40d30736c7cbe47" } } ], "extra": [ 1, 241, 177, 185, 51, 80, 137, 16, 163, 223, 62, 172, 172, 169, 98, 48, 158, 216, 87, 248, 108, 125, 163, 100, 14, 208, 221, 91, 34, 72, 23, 152, 113, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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