Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d18bfe4ef3fb400cdf80d155d6cdbc0874e2e7d0bc6a12024789eb7a0d23e493

Tx prefix hash: b1224b5ddea4a404baa78484838e4c3b461cace1261afd5da5e27094066eb4e4
Tx public key: 1fe1f81c21d9a6936e3b9210b83ca138a918f41a37746fb2da81a589ddc51c61
Timestamp: 1658143261 Timestamp [UCT]: 2022-07-18 11:21:01 Age [y:d:h:m:s]: 02:300:12:33:02
Block: 546395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 735972 RingCT/type: yes/0
Extra: 011fe1f81c21d9a6936e3b9210b83ca138a918f41a37746fb2da81a589ddc51c61021100000001bf7ee4e7000000000000000000

1 output(s) for total of 9.496568019000 dcy

stealth address amount amount idx
00: 4f3217ecd24b8f92f08857367278954ad8605033a586d82cb5ed6e6314a60924 9.496568019000 977404 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": 546405, "vin": [ { "gen": { "height": 546395 } } ], "vout": [ { "amount": 9496568019, "target": { "key": "4f3217ecd24b8f92f08857367278954ad8605033a586d82cb5ed6e6314a60924" } } ], "extra": [ 1, 31, 225, 248, 28, 33, 217, 166, 147, 110, 59, 146, 16, 184, 60, 161, 56, 169, 24, 244, 26, 55, 116, 111, 178, 218, 129, 165, 137, 221, 197, 28, 97, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 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