Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 060d94f60626026b89806830a9629b5878ebb256544e0daa332c7b23a9e7a573

Tx prefix hash: 133cec9be28558647b85af1fa252eec8c2f3f807205c6e85accf1c596643afb2
Tx public key: b7909a66faa459f1f1cdc9b4a0ebfb857db17d1ce5ea936c7c33b7a494d8a3a3
Timestamp: 1724278262 Timestamp [UCT]: 2024-08-21 22:11:02 Age [y:d:h:m:s]: 00:224:01:30:44
Block: 1093032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159984 RingCT/type: yes/0
Extra: 01b7909a66faa459f1f1cdc9b4a0ebfb857db17d1ce5ea936c7c33b7a494d8a3a302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51da1fd8f14fa3e7678d8049a3ddb8cf0f8480e67e5b154b1751e5024d26edc4 0.600000000000 1567895 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": 1093042, "vin": [ { "gen": { "height": 1093032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51da1fd8f14fa3e7678d8049a3ddb8cf0f8480e67e5b154b1751e5024d26edc4" } } ], "extra": [ 1, 183, 144, 154, 102, 250, 164, 89, 241, 241, 205, 201, 180, 160, 235, 251, 133, 125, 177, 125, 28, 229, 234, 147, 108, 124, 51, 183, 164, 148, 216, 163, 163, 2, 17, 0, 0, 0, 2, 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