Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0408a171a7bf72123103d702ee1833179928a5d37e1866ab5cc20cea1d76f1

Tx prefix hash: 686bda5341805f61b80abb1d6a313db390cf9d41fd2a5a5df1d977b7c581fba8
Tx public key: d6b7f05eb706fe72d6e6909d179dc94b127d29709ce5ad882e4a467d90c1d19d
Timestamp: 1632144448 Timestamp [UCT]: 2021-09-20 13:27:28 Age [y:d:h:m:s]: 03:255:20:35:59
Block: 337564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 958703 RingCT/type: yes/0
Extra: 01d6b7f05eb706fe72d6e6909d179dc94b127d29709ce5ad882e4a467d90c1d19d02110000003436fe6557000000000000000000

1 output(s) for total of 46.720854181000 dcy

stealth address amount amount idx
00: 90ef0bc93d8e88353cd5eb0b47ee84eaaf5095dee3a0417a8c26cf85ad684a5f 46.720854181000 695041 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": 337574, "vin": [ { "gen": { "height": 337564 } } ], "vout": [ { "amount": 46720854181, "target": { "key": "90ef0bc93d8e88353cd5eb0b47ee84eaaf5095dee3a0417a8c26cf85ad684a5f" } } ], "extra": [ 1, 214, 183, 240, 94, 183, 6, 254, 114, 214, 230, 144, 157, 23, 157, 201, 75, 18, 125, 41, 112, 156, 229, 173, 136, 46, 74, 70, 125, 144, 193, 209, 157, 2, 17, 0, 0, 0, 52, 54, 254, 101, 87, 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