Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f2beff5974a50da6216cf057afba2a95deffca3413cb4cf0ae8f39ab24e3fa8

Tx prefix hash: 10179ff743977d19f495fe5249d493cafd627c9b2bc2a234775f79adf1f8e0c0
Tx public key: 356bc138e50a212e8ddf5f7d037ce66c7ac0a4e49f26e4ba7a86aba9085838e1
Timestamp: 1713211303 Timestamp [UCT]: 2024-04-15 20:01:43 Age [y:d:h:m:s]: 01:016:19:55:45
Block: 1001254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272999 RingCT/type: yes/0
Extra: 01356bc138e50a212e8ddf5f7d037ce66c7ac0a4e49f26e4ba7a86aba9085838e10211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e19eb424ea2db4c70183f1491096c9ce1d31603de5b72a54ee066c127be63fb9 0.600000000000 1461758 of 15

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": 1001264, "vin": [ { "gen": { "height": 1001254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e19eb424ea2db4c70183f1491096c9ce1d31603de5b72a54ee066c127be63fb9" } } ], "extra": [ 1, 53, 107, 193, 56, 229, 10, 33, 46, 141, 223, 95, 125, 3, 124, 230, 108, 122, 192, 164, 228, 159, 38, 228, 186, 122, 134, 171, 169, 8, 88, 56, 225, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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