Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df473069ceec17e6cb818f8c5abb39b69399b32cab2190a130da7bc5414ff8c6

Tx prefix hash: d748ee9eb5042e54fab9b393d3df06f64faa60069364358ac0bcf8b907ef6659
Tx public key: 38a1f16882c887d0977de8c0d6211d6479ca721c31d6b6b53fe2845e25d8bb9a
Timestamp: 1707968632 Timestamp [UCT]: 2024-02-15 03:43:52 Age [y:d:h:m:s]: 01:048:04:41:56
Block: 957795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295487 RingCT/type: yes/0
Extra: 0138a1f16882c887d0977de8c0d6211d6479ca721c31d6b6b53fe2845e25d8bb9a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09280ecbffce37ece006e719130b3c98dcbca5a03a630bc0e5b68f6e29bb1f30 0.600000000000 1417146 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": 957805, "vin": [ { "gen": { "height": 957795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09280ecbffce37ece006e719130b3c98dcbca5a03a630bc0e5b68f6e29bb1f30" } } ], "extra": [ 1, 56, 161, 241, 104, 130, 200, 135, 208, 151, 125, 232, 192, 214, 33, 29, 100, 121, 202, 114, 28, 49, 214, 182, 181, 63, 226, 132, 94, 37, 216, 187, 154, 2, 17, 0, 0, 0, 1, 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