Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d85a14fb2de97d5fb7a62409381078bafe7a6fb147874236836b20413956170

Tx prefix hash: b19cf18bc9b86597c6e4dfe040c1df57548f3347e67e060f4cb9636c96b4d7df
Tx public key: aefc855e6c6567a7a81cf289f887f83c5e90dbb6f2c0a4e8451ceaac31af774b
Timestamp: 1707065974 Timestamp [UCT]: 2024-02-04 16:59:34 Age [y:d:h:m:s]: 01:024:03:33:29
Block: 950310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278289 RingCT/type: yes/0
Extra: 01aefc855e6c6567a7a81cf289f887f83c5e90dbb6f2c0a4e8451ceaac31af774b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e0696a59ed8e8a93c146fd6c878eea2d2c50038fbc04427e5552b259de50412 0.600000000000 1408908 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": 950320, "vin": [ { "gen": { "height": 950310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e0696a59ed8e8a93c146fd6c878eea2d2c50038fbc04427e5552b259de50412" } } ], "extra": [ 1, 174, 252, 133, 94, 108, 101, 103, 167, 168, 28, 242, 137, 248, 135, 248, 60, 94, 144, 219, 182, 242, 192, 164, 232, 69, 28, 234, 172, 49, 175, 119, 75, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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