Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1d9999c9eea231ed262d1f6dc7c715cce6193e9501945d24c15b694a8139d2a

Tx prefix hash: 2c23c0ea90a90c3855f524d39bb77b39afd21bd6bea48600622e72b5502fe4ad
Tx public key: 072a13f05b1e3cdafbd49222aa64dfa2a9322bdbedad4d0e4308bf2917e4c119
Timestamp: 1582933046 Timestamp [UCT]: 2020-02-28 23:37:26 Age [y:d:h:m:s]: 04:303:07:06:11
Block: 73681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110440 RingCT/type: yes/0
Extra: 01072a13f05b1e3cdafbd49222aa64dfa2a9322bdbedad4d0e4308bf2917e4c11902110000003d7adf42d3000000000000000000

1 output(s) for total of 349.860331977000 dcy

stealth address amount amount idx
00: d9a0964bcf8797a331c19194b2a078ed7bd323d03c95ce675843eb3b1ae3cd7a 349.860331977000 135966 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": 73691, "vin": [ { "gen": { "height": 73681 } } ], "vout": [ { "amount": 349860331977, "target": { "key": "d9a0964bcf8797a331c19194b2a078ed7bd323d03c95ce675843eb3b1ae3cd7a" } } ], "extra": [ 1, 7, 42, 19, 240, 91, 30, 60, 218, 251, 212, 146, 34, 170, 100, 223, 162, 169, 50, 43, 219, 237, 173, 77, 14, 67, 8, 191, 41, 23, 228, 193, 25, 2, 17, 0, 0, 0, 61, 122, 223, 66, 211, 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