Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f40c2fc0cec550fa66c07884cc4bc23bf064dfa4c2b2a3f4a797c9ca335538

Tx prefix hash: 2305e505b07946731e9cabf36a13671721fbb0c39faeb61ef40c268ee773120f
Tx public key: feb59d208b82d7e989d8de3de0cb6c0a8ff1f3865447bf944d51c1be0b4370d3
Timestamp: 1724857369 Timestamp [UCT]: 2024-08-28 15:02:49 Age [y:d:h:m:s]: 00:231:13:02:46
Block: 1097823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165345 RingCT/type: yes/0
Extra: 01feb59d208b82d7e989d8de3de0cb6c0a8ff1f3865447bf944d51c1be0b4370d3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82c1c3484d513ddf175f855c1660e965a06bd5ac452a4838892b7d8cc9b72bca 0.600000000000 1573326 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": 1097833, "vin": [ { "gen": { "height": 1097823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82c1c3484d513ddf175f855c1660e965a06bd5ac452a4838892b7d8cc9b72bca" } } ], "extra": [ 1, 254, 181, 157, 32, 139, 130, 215, 233, 137, 216, 222, 61, 224, 203, 108, 10, 143, 241, 243, 134, 84, 71, 191, 148, 77, 81, 193, 190, 11, 67, 112, 211, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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