Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2640ac2750eacf395fd8cafa4f822c5dc2f869f32025ad6517563dbc926ab0a8

Tx prefix hash: 0e51c12ef6d1093d5ab5ab3afe7ef8af2af16e869bbebedf32e447c7d96274b8
Tx public key: 32557961966de87b75336e0888f24c0c09e34a14d8557ac6c5366e3ba45b17e3
Timestamp: 1677892208 Timestamp [UCT]: 2023-03-04 01:10:08 Age [y:d:h:m:s]: 02:088:02:38:39
Block: 709351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584582 RingCT/type: yes/0
Extra: 0132557961966de87b75336e0888f24c0c09e34a14d8557ac6c5366e3ba45b17e30211000000035029cbac000000000000000000

1 output(s) for total of 2.739211530000 dcy

stealth address amount amount idx
00: 320ee1fe41bbf7b7513f5e8aa95a4a02b4fb19ae628a6c0edc6180be6555d74c 2.739211530000 1153330 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": 709361, "vin": [ { "gen": { "height": 709351 } } ], "vout": [ { "amount": 2739211530, "target": { "key": "320ee1fe41bbf7b7513f5e8aa95a4a02b4fb19ae628a6c0edc6180be6555d74c" } } ], "extra": [ 1, 50, 85, 121, 97, 150, 109, 232, 123, 117, 51, 110, 8, 136, 242, 76, 12, 9, 227, 74, 20, 216, 85, 122, 198, 197, 54, 110, 59, 164, 91, 23, 227, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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