Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be4ea375842ef6ae88ce0beea54d09d538d598b28171347ee217cd9e267bc1a3

Tx prefix hash: 583e5cc6872eda7216417dfa5795bce24fdaaf525c993f1efef256ad797fe0bc
Tx public key: 64dcb19b93f1bfd611bd5acf9fc8bc3e3316202e664498c8dc991121b7a8c51b
Timestamp: 1674248409 Timestamp [UCT]: 2023-01-20 21:00:09 Age [y:d:h:m:s]: 02:128:07:14:01
Block: 679123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 613388 RingCT/type: yes/0
Extra: 0164dcb19b93f1bfd611bd5acf9fc8bc3e3316202e664498c8dc991121b7a8c51b0211000000025029cbac000000000000000000

1 output(s) for total of 3.449717466000 dcy

stealth address amount amount idx
00: 327f942167404e500a1c3479b3129a3e5e9c2577580ed98e3f2cf01bc9ef5f22 3.449717466000 1121086 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": 679133, "vin": [ { "gen": { "height": 679123 } } ], "vout": [ { "amount": 3449717466, "target": { "key": "327f942167404e500a1c3479b3129a3e5e9c2577580ed98e3f2cf01bc9ef5f22" } } ], "extra": [ 1, 100, 220, 177, 155, 147, 241, 191, 214, 17, 189, 90, 207, 159, 200, 188, 62, 51, 22, 32, 46, 102, 68, 152, 200, 220, 153, 17, 33, 183, 168, 197, 27, 2, 17, 0, 0, 0, 2, 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