Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5e887d9afbb6df47b8a39fcd8ca8097b54e1ce038c4e77286e7ccc05539c187

Tx prefix hash: 05caf31daf5d0df8443b01cac741452ea2f9fb118aef4239eeb4cbbca2850d9d
Tx public key: 14a9b53de82256f01314be9ec049f6756399b4fccb5d457547dec30dd0b80e85
Timestamp: 1674156241 Timestamp [UCT]: 2023-01-19 19:24:01 Age [y:d:h:m:s]: 02:001:01:23:42
Block: 678349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522602 RingCT/type: yes/0
Extra: 0114a9b53de82256f01314be9ec049f6756399b4fccb5d457547dec30dd0b80e8502110000000352542ceb000000000000000000

1 output(s) for total of 3.470148913000 dcy

stealth address amount amount idx
00: 7a5d28ea9495741574924ed809b29b715fdae3c9f61d7891b1aacf05766375b9 3.470148913000 1120222 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": 678359, "vin": [ { "gen": { "height": 678349 } } ], "vout": [ { "amount": 3470148913, "target": { "key": "7a5d28ea9495741574924ed809b29b715fdae3c9f61d7891b1aacf05766375b9" } } ], "extra": [ 1, 20, 169, 181, 61, 232, 34, 86, 240, 19, 20, 190, 158, 192, 73, 246, 117, 99, 153, 180, 252, 203, 93, 69, 117, 71, 222, 195, 13, 208, 184, 14, 133, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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