Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0575c3524dc430dc289cbbbc57a4a0a0ebe917ecf630bee562108d88bdb742b

Tx prefix hash: 6e241066d5e2a1c95960e8feffcc09aa477cd5b682d6906edfd2185e9ecfab78
Tx public key: 27f36f03506bb8c800a39093a8ef1c7fc65f705f75b91ee408afb352a251947a
Timestamp: 1732880381 Timestamp [UCT]: 2024-11-29 11:39:41 Age [y:d:h:m:s]: 00:153:21:31:36
Block: 1164237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109821 RingCT/type: yes/0
Extra: 0127f36f03506bb8c800a39093a8ef1c7fc65f705f75b91ee408afb352a251947a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ca36636e5d104f4df7cc272a0a7eeadf93ae6bdf5c4d183f3dbde389a78a1b1 0.600000000000 1649910 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": 1164247, "vin": [ { "gen": { "height": 1164237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ca36636e5d104f4df7cc272a0a7eeadf93ae6bdf5c4d183f3dbde389a78a1b1" } } ], "extra": [ 1, 39, 243, 111, 3, 80, 107, 184, 200, 0, 163, 144, 147, 168, 239, 28, 127, 198, 95, 112, 95, 117, 185, 30, 228, 8, 175, 179, 82, 162, 81, 148, 122, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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