Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00641269510c27a9bdc21b61ccc8af5113517c2d402d738190356d25261d9776

Tx prefix hash: 7093e8345c74d2c9d3da7fd5b909b0721c44d4ea9c963ad7cc761450f2146e10
Tx public key: 51266c037589e8ecf443c8af3f684f94d540d3057f4f87a1ca6d20c441810f97
Timestamp: 1673556647 Timestamp [UCT]: 2023-01-12 20:50:47 Age [y:d:h:m:s]: 02:088:01:39:20
Block: 673374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584621 RingCT/type: yes/0
Extra: 0151266c037589e8ecf443c8af3f684f94d540d3057f4f87a1ca6d20c441810f970211000000014b0693a1000000000000000000

1 output(s) for total of 3.604394841000 dcy

stealth address amount amount idx
00: 33120a8c727a372f9d33e7c6192c3899477b9eddabad37a97da7e22442b687ef 3.604394841000 1114979 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": 673384, "vin": [ { "gen": { "height": 673374 } } ], "vout": [ { "amount": 3604394841, "target": { "key": "33120a8c727a372f9d33e7c6192c3899477b9eddabad37a97da7e22442b687ef" } } ], "extra": [ 1, 81, 38, 108, 3, 117, 137, 232, 236, 244, 67, 200, 175, 63, 104, 79, 148, 213, 64, 211, 5, 127, 79, 135, 161, 202, 109, 32, 196, 65, 129, 15, 151, 2, 17, 0, 0, 0, 1, 75, 6, 147, 161, 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